Description

• Added assign_yourself flag
• Option to auto-assign PR creator
• Added conditional step to assign PR opener

Type of Change

• 🐛 Bug fix
• ✨ New workflow
• 📝 Documentation update
• 🔧 Workflow enhancement
• 🎨 Code style/formatting
• ♻️ Refactoring
• ⚡ Performance improvement
• 🔒 Security improvement

Workflow Category

• Terraform (tf-*)
• CloudFormation (cf-*)
• Docker (docker-*)
• Helm (helm-*)
• PR Automation (pr-*)
• Security (security-*)
• Release (release-*)
• Notification (notify-*)
• AWS-specific (aws-*)
• GCP-specific (gcp-*)
• YAML Lint (yl-*)
• Other

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have updated the documentation accordingly
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published

Testing

• The current workflow (pr-auto-assignee.yml) does not support adding the PR-Owner as an assignee.
  My changes enable this functionality. The PR-Owner can now be automatically added as an assignee in same PR. This behavior can be controlled using the variable assign_yourself. Setting it to true will add the PR owner to the PR assignees (default is true).

Screenshots/Documentation

Related Issues

Closes #

Additional Notes